A Reference Architecture Primer

A Reference Architecture captures the essence of the architecture of a collection of systems. The purpose of a Reference Architecture is to provide guidance for the development of architectures for new versions of the system or extended systems and product families. We provide guidelines for the content of a Reference Architecture and the process to create and maintain it. A Reference Architecture is created by capturing the essentials of existing architectures and by taking into account future needs and opportunities, ranging from specific technologies, to patterns to business models and market segments. Distribution This article or presentation is written as part of the Gaudí project. The Gaudí project philosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by an open creation process. This document is published as intermediate or nearly mature version to get feedback. Further distribution is allowed as long as the document remains complete and unchanged. March 6, 2013 status: preliminary draft version: 0.6 family architecture product family system A system B system architecture shared assets shared asset architecture engineering documentation actual systems architectures reference architecture reference architecture architect design and engineer build and test field feedback constraints and opportunities extracting essentials 1. general introduction 2. level of abstraction 3. content 4. summary A Reference Architecture Primer 2 Gerrit Muller version: 0.6 March 6, 2013 RAPnavigation General Introduction to Reference Architectures Why R eference A rchitectures ? When to Use R eference A rchitectures ? What do R eference A rchitectures contain? How to use R eference A rchitectures ? What are inputs of a R eference A rchitecture ? Criteria for a good R eference A rchitecture. A Reference Architecture Primer 3 Gerrit Muller version: 0.6 March 6, 2013 RAPintro Graph of objectives of Reference Architectures increased dynamics integration increased complexity scope size Facilitate multi-site multi-organization multi-vendor multi-* system creation and life-cycle support Effectively create new: products product lines product portfolio managing synergy Achieve interoperability between many different and evolving systems providing guidance , e.g. architecture principles, best practices providing an architecture baseline and an architecture blueprint capturing and sharing (architectural) patterns providing a common (architectural) vision providing a common lexicon and taxonomy providing modularization and the complementary context Articulation of domain and realization concepts Explicit decisions about compatibility, upgrade and interchangeability. Explicit modeling of functions and qualities above systems level A Reference Architecture Primer 4 Gerrit Muller version: 0.6 March 6, 2013 SAFRAwhy When to Use Reference Architectures multi-site multi-supplier multi-vendor mono-disciplinary engineering mono-system design mono-system architecting product family architecting evolvable product family architecting Reference Architecture Reference Architectures facilitate the step towards product family architecting and evolvability; this often coincides with multi-* problems A Reference Architecture Primer 5 Gerrit Muller version: 0.6 March 6, 2013 RAPwhen RA Elaborates Mission, Vision and Strategy mission